EMail: magneoe@stud.cs.uit.no
PoolWatch is especially useful in combination with Enforcer, Mungwall (which will watch normal allocations that use AllocMem/FreeMem), SegTracker and FindHit (included in the Enforcer archive).
If SegTracker is running in the system when PoolWatch is started, PoolWatch will use the public SegTracker seglist tracking for identifying the hunk and offset into the executable doing illegal allocations.
PoolWatch will patch CreatePool(), DeletePool(), AllocPooled(), and FreePooled() in exec.library. PoolWatch will use these functions but will add extra security on top of all pool-allocations. In most cases of illegal allocation/freeing, PoolWatch will report the error to the user and correct the problem (if possible). Please note that PoolWatch does not offer any memory protection if a task writes to a random addresse in memory, but will take care of most problems associated with pool allocations.